I migrated the nix derivation from poetry to uv and refactored the nix derivations at the same time. I also added uv2nix and pyproject-build-systems to the devops configuration for periodic update pull requests, see runtimeverification/devops#242.

I also fixed the broken nix develop shell and refactored the dependencies of both the nix develop shell and kevm derivation.

While doing so, I noticed that the derivation is built with g++. I think that clang might be preferred here for performance reasons. In fact, clang was/is included in the dependencies of the derivation, but not used. To switch out the compiler that is used by default, you typically swap out pkgs.stdenv.mkDerivation with pkgs.clangStdenv.mkDerivation. At the same time, clang cannot actually be removed from the dependencies, because the blockchain-k-plugin build fails if the ar binary is used from gcc instead the ar binary from clang. The build fails somewhere inbetween because the make process ends up in a directory that is then removed, before the make process leaves the directory. Besides that, I didn't debug any further. Again, we might wanna switch to clang entirely anyway. The same should apply for the kontrol derivation.

@tothtamas28 Please review the nix part and workflows that I worked on. I can't request a review from you as you are the PR owner.